We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Describe the bug The readiness API returns inconsistent results across multiple versions
nacosv2-0:/home/nacos# curl 127.0.0.1:8848/nacos/v2/console/health/readiness -v * Trying 127.0.0.1:8848... * Connected to 127.0.0.1 (127.0.0.1) port 8848 * using HTTP/1.x > GET /nacos/v2/console/health/readiness HTTP/1.1 > Host: 127.0.0.1:8848 > User-Agent: curl/8.12.1 > Accept: */* > * Request completely sent off < HTTP/1.1 200 < Vary: Origin < Vary: Access-Control-Request-Method < Vary: Access-Control-Request-Headers < Content-Security-Policy: script-src 'self' < Content-Type: application/json < Transfer-Encoding: chunked < Date: Tue, 27 May 2025 05:34:06 GMT < * Connection #0 to host 127.0.0.1 left intact {"code":30000,"message":"naming not in readiness","data":null}nacosv2-0:/home/nacos# nacosv2-0:/home/nacos# nacosv2-0:/home/nacos# nacosv2-0:/home/nacos# nacosv2-0:/home/nacos# nacosv2-0:/home/nacos# curl 127.0.0.1:8848/nacos/v1/console/health/readiness -v * Trying 127.0.0.1:8848... * Connected to 127.0.0.1 (127.0.0.1) port 8848 * using HTTP/1.x > GET /nacos/v1/console/health/readiness HTTP/1.1 > Host: 127.0.0.1:8848 > User-Agent: curl/8.12.1 > Accept: */* > * Request completely sent off < HTTP/1.1 500 < Vary: Origin < Vary: Access-Control-Request-Method < Vary: Access-Control-Request-Headers < Content-Security-Policy: script-src 'self' < Content-Type: text/plain;charset=UTF-8 < Content-Length: 23 < Date: Tue, 27 May 2025 05:34:10 GMT < Connection: close < * shutting down connection #0 naming not in readiness
Expected behavior all both return 200
Actually behavior 200 and 500
How to Reproduce Steps to reproduce the behavior:
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered:
v1 and v2 API will deprecated in 3.1.0.
suggest you use v3 api.
Sorry, something went wrong.
also need check the v3 api whether return 200 when readiness is not pass.
3.1 什么时候发版?
No branches or pull requests
Describe the bug
The readiness API returns inconsistent results across multiple versions
Expected behavior
all both return 200
Actually behavior
200 and 500
How to Reproduce
Steps to reproduce the behavior:
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: